Jira link

See HDPI-3395)

Change description

Added option to use /case-user endpoint on ccd without having to pass a user that is in an organisation.
I have done this by:

1. Renaming CaseAssignmentUserRolesRequest --> CaseAssignmentUserRolesWithOrgansiationRequest
2. Method overloading addCaseUserRoles with the passing of CaseAssignmentUserRoleResource

Testing done

Tested the endpoint accepts this data via postman with the following curl:
curl --location 'localhost:4452/case-users' \ --header 'accept: */*' \ --header 'Authorization: userToken' \ --header 'ServiceAuthorization: serviceToken' \ --header 'Content-Type: application/json' \ --header 'Cookie: XSRF-TOKEN=iPfBmv3q-m8el0LCZT773bytvKy5tXbrbq0o; xui-webapp=s%3Ah8893v7YuZLkNpWiMQIKfbL8Sc3YfNzS.slqlFSH%2FE%2BUKiSN40gVSpOardJLkuj%2FB0Q8Y1HgFyFk' \ --data '{ "case_users": [ { "case_id": "1764867117280426", "case_role": "[DEFENDANT]", "user_id": "9a2d861a-6264-4765-9f61-1d403079f71b" } ] }'

In addition to testing via my local branch of pcs-api utilising the changes in this PR.

Security Vulnerability Assessment

CVE Suppression: Are there any CVEs present in the codebase (either newly introduced or pre-existing) that are being intentionally suppressed or ignored by this commit?

• Yes
• No

Checklist

• commit messages are meaningful and follow good commit message guidelines
• [x]not needed
• [x]not needed
• Does this PR introduce a breaking change